View SPBT2532C2AT_4185792.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

august 2009 doc id 16089 rev 1 1/51 51 spbt2532c2.at bluetooth ? technology class-2 module features bluetooth ? specification compliant v2.1 output power class-2 transmission rate up to 2 mbps with edr point-to-point packet types supported: ? acl: dm1, dm3, dm5, dh1, dh3, dh5, 2- dh1, 2-dh3, 2-dh5 adaptive frequency hopping (afh) efficient and flexible support for wlan coexistence in collocated scenario communication interfaces: (a) ? fast uart up to 3.25 mbit/s ? spi interface ?i 2 c interface ?i 2 s interface general i/o: (a) ? 4 general purpose i/o ? 4 x 12-bit a/d input user interface: ? at command set memory: ? 256 kbytes flash memory ? 48 kbytes ram memory 3.3 v single supply voltage no external oscillator required module size: 10 x 13 mm description the spbt2532c2.at is a surface-mount pcb module that provides fully embedded, ready-to-use bluetooth wireless technology. it is designed for maximum performance in a minimal space and includes 4 general purpose (a) and 4 a/d io lines (a) , several serial interface options (a) , and up to 2 mbps data throughput. the re-programmable flash memory contains embedded firmware for serial cable replacement using the bluetooth spp profile. a. all these resources cannot coexist at the same time; they are shared on the 8 pins available for interface. standard configuration for at command set is 4 pins for uart and 4 pins for gpio. www.st.com
contents spbt2532c2.at 2/51 doc id 16089 rev 1 contents 1 rohs compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2 application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4 maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.1 absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.2 operating ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3 power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5 electrical characteristi cs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.1 dc i/o specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6 bluetooth parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6.1 rf performance characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 7 pin settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.1 pin connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.2 pin description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 8 software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8.1 lower layer stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8.2 upper layer stack: amp?ed up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8.3 at command set: abserial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 9 hardware design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9.1 component drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9.2 uart interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 9.3 typical circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 10 soldering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 appendix a certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
spbt2532c2.at contents doc id 16089 rev 1 3/51 a.1 fcc compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 appendix b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 b.1 purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 b.2 definitions and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 b.3 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 b.4 abserial interface overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 b.5 factory defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 appendix c commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 c.1 bond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 c.1.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 c.1.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 c.2 build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.2.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.2.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.3 bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.3.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.3.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.4 changebaud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.4.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 c.4.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 c.5 changedefaultbaud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 c.5.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 c.5.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 c.6 defaultlocalname. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 c.6.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 c.6.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 c.7 deletesmartcable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 c.7.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 c.7.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 c.8 disablebond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 c.8.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 c.8.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 c.9 discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 c.9.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
contents spbt2532c2.at 4/51 doc id 16089 rev 1 c.9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . responses30 c.10 dunconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 c.10.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 c.10.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 c.11 dundisconnect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 c.11.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 c.11.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 c.12 enablebond. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 c.12.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 c.12.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 c.13 erasebondtable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.13.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.13.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.14 exitpark . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.14.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.14.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.15 exitsniff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.15.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.15.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 c.16 gpioconfig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.16.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.16.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.17 gpioread. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.17.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.17.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.18 gpiowrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.18.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.18.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 c.19 hold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 c.19.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 c.19.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 c.20 hostevent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 c.20.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 c.20.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 c.21 localname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 c.21.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
spbt2532c2.at contents doc id 16089 rev 1 5/51 c.21.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 c.22 park . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 c.22.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 c.22.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 c.23 remotecommand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 c.23.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 c.23.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 c.24 remotecmddisconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.24.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.24.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.25 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.25.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.25.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.26 security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.26.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 c.26.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 c.27 smartcablesetup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 c.27.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 c.27.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 c.28 sniff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 c.28.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 c.28.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 c.29 sppconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 c.29.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 c.29.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 c.30 sppdisconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 c.30.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 c.30.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 c.31 streamingserial. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 c.31.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 c.31.2 query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 c.31.3 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 c.32 updateinquiryscan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 c.32.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 c.32.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 c.33 updatepagescan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
contents spbt2532c2.at 6/51 doc id 16089 rev 1 c.33.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 c.33.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 c.34 version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 c.34.1 syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 c.34.2 responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 appendix d error responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 d.1 errconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 d.2 errexecution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 d.3 errformat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 d.4 errinvalidparam. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 d.5 errnumparam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 d.6 errunknowncmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 d.7 errinprogress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 d.8 commands and associated errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 appendix e other responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 e.1 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 e.2 escape sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 e.3 controlled disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 e.4 unexpected disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 ordering information scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
spbt2532c2.at rohs compliance doc id 16089 rev 1 7/51 1 rohs compliance st modules are rohs compliant and being based on st devices comply with ecopack ? norms implemented by st. 2 application serial cable replacement industrial control medical pos terminals data acquisition equipment internet access points machine control sensor monitoring robotic and bionic control security control patient monitoring audio gateway applications hands-free sets wireless printers cordless terminals laptops, pcs and accessories handheld devices and accessories hid devices (keyboard, mouse, joystick, game controller?)
block diagram spbt2532c2.at 8/51 doc id 16089 rev 1 3 block diagram figure 1. block diagram !-v
spbt2532c2.at maximum ratings doc id 16089 rev 1 9/51 4 maximum ratings 4.1 absolute maximum ratings 4.2 operating ranges operating ranges define the limits for functional operation and parametric characteristics of the module. functionality outside thes e limits is not implied table 1. absolute maximum ratings rating min typ max unit storage temperature range -55 - +105 c supply voltage, v in -0.3 - + 5.0 v rf input power - - +10 dbm input voltage on 5 v tolerant pin -0.3 - +5.5 v input voltage on non-5 v tolerant pin -0.3 - +4.0 v table 2. operating ranges rating min typ max unit operating temperature range -40 - 85 c supply voltage v in 2.7 3.0 3.6 v signal pin voltage - 3.0 - v rf frequency 2400 - 2483.5 mhz
maximum ratings spbt2532c2.at 10/51 doc id 16089 rev 1 4.3 power consumption cpu 32 mhz uart supports up to 921 kbps data throughput up to 2 mbps table 3. high speed cpu mode modes avg unit typical power consumption acl data 115 kbaud uart at max throughput (master) 41.0 ma acl data 115 kbaud uart at max throughput (slave) 41.0 ma connection, no data traffic, master 28.9 ma connection, no data traffic, slave 35.4 ma standby, and page/inquiry scan, without deep sleep 28.0 ma standby, and page/inquiry scan, with deep sleep 3.5 ma
spbt2532c2.at electrical characteristics doc id 16089 rev 1 11/51 5 electrical characteristics 5.1 dc i/o specification table 4. dc input / output specification symbol parameter conditions min max unit v il low-level input voltage v in = 3.0 v (pin 8) - 0.9 v v ih high-level input voltage v in = 3.0 v (pin 8) 2.1 - v ol low-level output voltage v in = 3.0 v (pin 8) - 0.4 v oh high-level output voltage v in = 3.0 v (pin 8) 2.2 - i ol low-level output current v ol = 0.4 v - 4.0 ma i oh high-level output current v oh = 2.2 v - 4.0 r pu pull-up resistor resistor turned on 80 120 k r pd pull-down resistor resistor turned on 80 120
bluetooth parameters spbt2532c2.at 12/51 doc id 16089 rev 1 6 bluetooth parameters 6.1 rf performance characteristics in the performance characteristics table the following applies: test condition: nominal voltage: typical, v in = 3.0 v temperature: typical t a = 25 c note: for more complete data, please refer to stm stlc2500d datasheet. table 5. rf performance characteristics parameters conditions bt spec typical unit antenna load 50 radio receiver sensitivity level ber < 0.001 with dh5 -70 -85 dbm maximum usable level ber < 0.001 with dh1 -20 +8 dbm input vswr 2.5:1 radio transmitter maximum output power 50 load -6 to +4 0 dbm initial carrier frequency tolerance 75 0 khz 20 db bandwidth for modulated carrier 1000 930 khz
spbt2532c2.at pin settings doc id 16089 rev 1 13/51 7 pin settings 7.1 pin connections figure 2. pin connection diagram
pin settings spbt2532c2.at 14/51 doc id 16089 rev 1 7.2 pin description table 6. pin description pin n name type description alt function uart interface 13 rxd i receive data adc3 14 txd o transmit data adc2 11 cts i clear to send (active low) adc0/i 2 c data/aux uart rx 12 rts o request to send (active low) adc1/i 2 c clock/aux uart tx antenna 6 ant rf i/o 50 rx/tx antenna port reserved 9 reserved i boot 0 power and ground 8v in v in 5, 7 gnd gnd reset 10 resetn i reset input (active low for 5 ms); gpio ? general purpose input/output 1 gpio [1] i/o general purpose input/output spi miso 2 gpio [2] i/o general purpose input/output spi mosi/i 2 s_sd 3 gpio [3] i/o general purpose input/output spi sclk/ i 2 s_ck 4 gpio [4] i/o general purpose input/output spi ss/i 2 s_ws
spbt2532c2.at software architecture doc id 16089 rev 1 15/51 8 software architecture the spbt2532c2.at includes th e bluetooth full protocol st ack with upper layers and profiles. figure 3. bluetooth firmware implementation
software architecture spbt2532c2.at 16/51 doc id 16089 rev 1 8.1 lower layer stack full bluetooth v2.1 data rate (3m bps maximum) device power modes?active, sleep and deep sleep wake on bluetooth feature?optimized power consumption of host cpu authentication and encryption encryption key length from 8-bits to 128-bits maximum persistent flash memory?for bd address and radio parameter storage acl (asynchronous connection less) packet types (dm1, dh1, dm3, dh3, dm5, dh5, 2-dh1, 2-dh3, 2-dh5) point to point support park, sniff, and hold modes?fully supported to maximum allowed intervals (see appendix b: ) master slave switch?supported during connection and post connection dedicated inquiry access code?for improved inquiry scan performance dynamic packet selection?channel quality driven data rate to optimize link performance dynamic power control?interference reduction and link performance bluetooth test modes?per bluetooth v2.0 specification 802.11b/g co-existence?awma and afh vendor specific hci commands?to support device configuration and certification test modes 8.2 upper layer stack: amp?ed up spp, sdap, gap protocols rfcomm, sdp, and l2cap supported 8.3 at command set: abserial please see appendix b: abserial reference guide for details
spbt2532c2.at hardware design doc id 16089 rev 1 17/51 9 hardware design notes : all unused pins should be left floating; do not ground. all gnd pins must be well grounded. traces should not be routed underneath the module. 9.1 component drawing figure 4. pin placement figure 5. ground plane diagram
hardware design spbt2532c2.at 18/51 doc id 16089 rev 1 9.2 uart interface the uart is compatible with the 16550 industry standard. four signals are provided with the uart interface. the txd and rxd pins are used for data while the cts and rts pins are used for flow control. figure 6. connection to host device 9.3 typical circuit figure 7. typical rs232 circuit
spbt2532c2.at soldering doc id 16089 rev 1 19/51 10 soldering soldering phase has to be executed with care: in order to avoid undesired melting phenomenon, particular attention has to be taken on the set up of the peak temperature. here following some suggestions for the temperature profile based on ipc/jedec j-std-020c, july 2004 recommendations. figure 8. soldering table 7. soldering profile feature pb-free assembly average ramp up rate (t smax to t p ) 3c / sec max preheat temperature min (t s min) temperature max (t s max) time (t s min to t s max) (t s ) 150 c 200 c 60-100 sec time maintained above: temperature t l time t l 217 c 60-70 sec peak temperature (t p ) 240 + 0 c time within 5 c of actual peak temperature (t p ) 10-20 sec ramp down rate 6 c / sec time from 25 c to peak temperature 8 minutes max
certifications spbt2532c2.at 20/51 doc id 16089 rev 1 appendix a certifications a.1 fcc compliance fcc licensing is dependent on final antenna implementation. many tests do not need to be repeated for final compliance and certification.
spbt2532c2.at doc id 16089 rev 1 21/51 appendix b the appendix describes an embedded application that provides a serial cable replacement service using the bluetooth serial port profile. b.1 purpose this document provides a detailed description of each command supported by the at command interface, (abserial) sw developed by amp?edrf. 654 figure 9. sw developer each description explains parameters and the expected behaviors of each command and response. errors responses are also detailed in this document. to provide feedback or to request assistance on abserial commands please contact abserial.support@st.com b.2 definitions and acronyms the following acronyms are used in this document. table 8. definitions and acronyms term description/meaning ascii american standard code for information interchange, a standard describing encoding of characters; the use in this document is strictly us 7-bit bd bluetooth device dcd modem signal ?data carrier detect?; indication from a modem that a connection has been made through, for example, a dialup connection dte data terminal entity, e.g., a computer dtr modem signal ?data terminal ready?; indication to a modem that the data terminal is ready for a connection dun dialup networking (profile) gpio general purpose input-output lan local area network pin personal identification number spp serial port profile uart universal asynchron ous receiver-transmitter
spbt2532c2.at 22/51 doc id 16089 rev 1 b.3 overview this chapter gives a basic overview of the abserial interface. for further information, please refer to the abserial user guide. b.4 abserial interface overview abserial is a cable replacement application that provides point-to-point communication between two bluetooth devices. a serial port is used to communicate with a host device through an at command interface as shown below. figure 10. communications between hosts abserial provides the following basic features: point-to-point connection ? abserial only supports a connection with one device at a time. ? optional multipoint applications are available upon request serial port profile ? spp is supported wit h abserial for both client and server application. ? optional dial up networking ? dun prof ile support for client applications (dun server is not currently supported). ? optional obex profiles ar e available upon request command and bypass modes ? it is possible to switch between command and bypass (data transmit/receive) modes during an active connection security ? bonding and data encryption provides a secure link between two devices. multiple device bonding ? special security keys can be exchanged with multiple devices to allow different devices to securely connect with abserial. power conservation ? use of the sniff feature to minimize power consumption. variable baud rates ? the serial port can be configured for the following baud rates: 1200, 2400, 4800, 9600, 19.2k, 38.4k, 57.6k, 115.2k (default), 230.4k, 460.8k, 921.6k (not available on all platforms) at ? cmds ? host ? device ? bluetooth device ? bluetooth ? device ?
spbt2532c2.at doc id 16089 rev 1 23/51 b.5 factory defaults the follow factory defaults are typically shipped with our standard products. customized defaults may be ordered upon request. uart: 115200 baud, no parity, 1 stop bit, 8 data bits local name: ?amp?ed up!? class of device: misc device profile: spp (serial port profile) service name: ?amp-spp? deep sleep: disabled page and inquiry scan: 1.28 s interval, 11 ms duration security: disabled bonding pin: ?1234? bonding allowed: always enabled
commands spbt2532c2.at 24/51 doc id 16089 rev 1 appendix c commands this chapter details the each of the abserial at commands including brief descriptions of behavior, syntax of the command, context of the command, and types of responses. this abserial reference guide covers the following commands: ta bl e key : ? command is supported in this release u ? command has been updated for this release, see release notes x ? command not supported in this release table 9. abserial command summary command abserial v1.1 bond build bypass changebaud changedefaultbaud defaultlocalname deletesmartcable disablebond discovery dunconnect x dundisconnect x enablebond erasebondtable exitpart exitsniff gpioconfig gpioread gpiowrite hold hostevent localname park remotecommand remotecmddisconnect reset
spbt2532c2.at commands doc id 16089 rev 1 25/51 the following subsections describe each of these commands in detail, including a description of behavior, syntax (including possible parameter values), and types of responses. some responses will not be ?imme diate?. where applicable, these will be noted and will include an approximate delay before response. for commands with optional parame ters, all possible forms will be listed under the syntax subsection. error responses are described in appendix d error responses . c.1 bond the bond command is used to initiate bonding with a specified device. a personal identification number (pin) is also required with this command. c.1.1 syntax at+ab bond [bd addr] [pin] where [bd addr] is the bd address of the remote device with which to bond and [pin] is the pin code to use (up to 16 characters). c.1.2 responses if the request is successfully submitted, the response is: at-ab bondpending [bd addr] if the operation is successful, the response is: at-ab bondok if the operation fails, the response is: at-ab bondfail command abserial v1.1 security smartcablesetup sniff sppconnect sppdisconnect streamingserial updateinquiryscan updatepagescan version u table 9. abserial command summary (continued)
commands spbt2532c2.at 26/51 doc id 16089 rev 1 c.2 build the version command is used to return the current version of the abserial interface. c.2.1 syntax at+ab build c.2.2 responses if the operation is successful, the response is: at-ab abserial build [date] where [date] is the date code of the application firmware. c.3 bypass the bypass command is used to return the abserial interface to the bypass mode, if a connection is still available. the possible use for this is to change a setting after a connection has been made (such as the uart ba ud rate). if the abserial interface does not have a connection, it will respond as if the connection is down. c.3.1 syntax at+ab bypass c.3.2 responses if a connection is still av ailable, the response is: at-ab -bypassmode- if there is currently no connection, the response is: at-ab connectiondown c.4 changebaud the host sends the changebaud command in order to change the local uart speed to a new speed identified by the host. this setting will only remain in effe ct during the current session - until reset. c.4.1 syntax at+ab changebaud [rate]
spbt2532c2.at commands doc id 16089 rev 1 27/51 where [rate] is the new baud rate: 2400 4800 9600 19,200 38,400 57,600 115,200 230,400 460,800 921,600 (not available on all platforms) c.4.2 responses if the change is accepted, the response is: at-ab baudrate changed the actual change will not occu r until the response has be en completely transmitted. c.5 changedefaultbaud the host sends the changedefaultbaud command in order to change the default uart speed to a new speed identified by the host. this command is used to override the default baud rate from the dynamic configuration script so that the device does not require reprogramming to update this setting. the new baud rate is updated permanently until the device is either re-programmed or another changedefaultbaud command is issued. the baud rate specified in the command will not take effect until the device is reset. to change the baud rate of the current session, use the changebaud command. c.5.1 syntax at+ab changedefaultbaud [rate] where [rate] is the new baud rate: 2400 4800 9,600 19,200 38,400 57,600 115,200 230,400 460,800 921,600
commands spbt2532c2.at 28/51 doc id 16089 rev 1 c.5.2 responses if the change is accepted, the response is: at-ab baudrate changed c.6 defaultlocalname the defaultlocalname command is used to set the name of the device to the name that is reported during device discoveries. by default, the abserial interface uses ?amp?edbtdevice?. changing the name using this command will permanently change the local name, unlike the localname command. c.6.1 syntax at+ab defaultlocalname [name] where [name] is a string for the new local name (up to 50 characters). the space character is allowed; the name is assumed to be all text up to the end of the command. c.6.2 responses if the operation is successful, the response is: at-ab localnameok c.7 deletesmartcable the deletesmartcable command removes the current smart cable settings that were entered using the smartcablesetup command, but not the setting from the dynamic configuration. the smart cable will then be deactivated for the remainder of this session. upon reset, if a dynami c configuration for a smart cable exis ts, it will be activated. if there is no dynamic configuration smart cable setup, then this feature will remain deactivated. c.7.1 syntax at+ab deletesmartcable c.7.2 responses if the operation is successful, the response is: at-ab deletesmartcabledone
spbt2532c2.at commands doc id 16089 rev 1 29/51 c.8 disablebond the disablebond command is used to disallow new bonding with a device. this command cannot be used while a connection is active. c.8.1 syntax at+ab disablebond c.8.2 responses if the operation is successful, the response is: at-ab bonddisabled c.9 discovery the discovery command is used to initiate a device discover y. the command will return the number of responses of nearby devices and th en the individual responses with bd address, name of device, and service names - optional. the number of devices returned is limited to 10; and the number of services per device is limited to 8. inquiry is performed with an interval of 10.24 seconds. the devices are reported in the same order as the original inquiry results. c.9.1 syntax at+ab discovery at+ab discovery [cod] at+ab discovery [cod] [profile] [include service enable/disable] where devices are filtered on the [cod] class: all (default) misc computer phone lan peripheral imaging unclass where the service name is requested for the profile named [profile]: all (default) spp dun lap fax
commands spbt2532c2.at 30/51 doc id 16089 rev 1 where [include service enable/disable]: true returns both the remote services and names, and false skips the remote service discovery and only returns the remote names ? this completes the discovery process faster. c.9.2 responses when the discovery command has been accepted, the response is: at-ab inqpending once the initial inquiry is co mplete and discovery has been started, the response is: at-ab discoverypending [num] where [num] is the number of devices found, in decimal (up to 10 will be reported). for each name or service name request that is successful, the response uses the returned names in the following format. at-ab device [bd addr] [name] [service name] [...] where [bd addr] is in hexadecimal with the most significant byte first. [name] is a string in double quotes ? ?. [service name] is a string without quotes and is reported for each service reported. for each unsuccessful name request, the corresponding name is replaced by unknown. the name request may not be successful if unable to make a connection for the request. at-ab device [bd addr] unknown [service name] [...] for each service request that does not return services, one name is returned as nosvcs . a request may not return services if unable to connect to the device for the request or if the device does not contain the requested service. at-ab device [bd addr] [name] nosvcs for each unsuccessful service request, one name is returned as svfail . this will only occur due to an internal error. at-ab device [bd addr] [name] svfail
spbt2532c2.at commands doc id 16089 rev 1 31/51 c.10 dunconnect the dunconnect command is used to initiate a connection with the specified device. the remote bd address must be specified. the remo te service is optional. if not specified, the first registered dun service will be used by default. c.10.1 syntax at+ab dunconnect [bd addr] [service] where [bd addr] is the remote devices bd address to page . [service] is the specific service on the remote device; optional. c.10.2 responses if the connection is successful, the response is: at-ab connectionup at-ab -bypassmode- if the connection cannot be completed, the response is: at-ab dunconnectionclosed c.11 dundisconnect the dundisconnect command is used to termi nate a connection with the remote device. c.11.1 syntax at+ab dundisconnect c.11.2 responses if the connection is successful, the response is: at-ab dunconnectionclosed
commands spbt2532c2.at 32/51 doc id 16089 rev 1 c.12 enablebond the enablebond command is used to enable bonding with another device. the bd address, pin and timeout parameters are optional. when no bd address is specified, requests from all bd addresses are allowed. if a bd address is specified, bonding requests from devices with bd addresses other than the one specified will fail and the existing link key will be deleted for that device. optionally, a pin code may be entered with this command. if no pin code is specified, the default pin code will be used. the default pin code is either the last 4 digits of the device?s bd address or the dynamically configured pin code, depending on the default pin selection in the dynamic configuration file. also, a timeout value, in seconds, may be entered after the pin code. bonding will be disabled automatically after the requested timeout. if no timeout is specified, bonding is enabled until reset or until the disablebond command is used. if this command is issued multiple times, only the last pin and bd address are saved. also, if this command is issued before the firs t timeout occurs, the subsequent command will extend the timeout. the timeout is always set to the specified time beyond the last received enablebond. c.12.1 syntax at+ab enablebond at+ab enablebond [bd addr] at+ab enablebond [bd addr] [pin] at+ab enablebond [bd addr] [pin] [timeout] where [bd addr] is the bd address of the remote device with which to bond, [pin] is the pin code to use (up to 16 characters), and [timeout] is the duration of the timeout in seconds (1 to 14,4 00, in decimal). c.12.2 responses if the operation is successful, the response is: at-ab bondenabled if bonding has been initiated by a remote device, the notification is: at-ab bondpending [bd addr] where [bd addr] is the bd address of the remote device that initiated the bonding. if bonding has occurred, the notification is: at-ab bondok [bd addr] where [bd addr] is the bd address of the remote device with successful bonding. if bonding was initiated by a remote device but failed, the notification is at-ab bondfail when the time limit for bonding has expired, the notification is at-ab bonddisabled
spbt2532c2.at commands doc id 16089 rev 1 33/51 c.13 erasebondtable the erasebondtable command is used to erase all of the bonded device entries. single devices cannot be erased with this command c.13.1 syntax at+ab erasebondtable c.13.2 responses if the operation is successful, the response is: at-ab bondtableerased c.14 exitpark the exitpark command is used to switch a device from park mode to active mode. c.14.1 syntax at+ab exitpark [bd address] where [bd address] is the bd address of the device to be switched to active mode. c.14.2 responses if the operation is successful, the response is: at-ab activemode c.15 exitsniff the exitsniff command is used to switch a device from sniff mode to active mode. c.15.1 syntax at+ab exitsniff [bd address] where [bd address] is the bd address of the device to be switched to active mode. c.15.2 responses if the operation is successful, the response is: at-ab activemode
commands spbt2532c2.at 34/51 doc id 16089 rev 1 c.16 gpioconfig the gpioconfig command is used to configure a gpio pin to input or output. c.16.1 syntax at+ab gpioconfig [gpio pin] [configuration] where [gpio pin] is the pin number, 1 ? 4, of the desired gpio to configure. [configuration] is i or i for input and o or o for output. c.16.2 responses if the operation is successful, the response is: at-ab gpioconfigdone c.17 gpioread the gpioread command is used to read a gpio pin. a gpio may be read while configured as either an input or output. c.17.1 syntax at+ab gpioread [gpio pin] where [gpio pin] is the pin number, 1 ? 4, of the desired gpio to read. c.17.2 responses if the operation is successful, the response is: at-ab gpioreaddone [result] where [result] is either a 1 to indicate high, or 0 to indicate low. c.18 gpiowrite the gpiowrite command is used to set a gpio pin to high or low. a gpio may only be set when configured as an output. c.18.1 syntax at+ab gpiowrite [gpio pin] [setting] where [gpio pin] is the pin number, 1 ? 4, of the desired gpio to read. [setting] is a 1 to set a pin to high and a 0 to set a pin to low. c.18.2 responses if the operation is successful, the response is: at-ab gpiowritedone
spbt2532c2.at commands doc id 16089 rev 1 35/51 c.19 hold the hold command is used to switch a device from active mode to hold mode. c.19.1 syntax at+ab hold [bd address] [hold duration] where [bd address] is the bd address of the device to be switched to active mode. [hold duration] is given in slots from 4-10,000. c.19.2 responses if the operation is successful, the response is: at-ab holdmode c.20 hostevent the hostevent command is used to enable/disable the host notification strings. this will override the default setting in the dynamic configuration only for the current session; until reset. c.20.1 syntax at+ab hostevent [enable/disable] where [enable/disable] is an e or e character to enable this parameter and a d or d character to disable it. c.20.2 responses if the feature is successfully enabled, the response is: at-ab hostevent enabled if the feature is successfully disabled there is no response because the events have been disabled. c.21 localname the localname command is used to set the name of the device to the name that is reported during device discoveries. by default, the abserial interface uses amp?edbtdevice. changing the name using this command does not permanently change the local name. c.21.1 syntax at+ab localname [name] where [name] is a string for the new local name (up to 50 characters). the space character is allowed; the name is assumed to be all text up to the end of the command.
commands spbt2532c2.at 36/51 doc id 16089 rev 1 c.21.2 responses if the operation is successful, the response is: at-ab localnameok c.22 park the park command is used to switch a device from active mode to park mode. c.22.1 syntax at+ab park [bd address] [beacon period] where [bd address] is the bd address of the device to be switched to active mode. [beacon period] is given in slots from 200-10,000. c.22.2 responses if the operation is successful, the response is: at-ab parkmode c.23 remotecommand the remotecommand command is used to enable/disable the remote command mode. this setting is stored in persistent memory, and will be retained after ea ch reset. additionally, the new setting will take ef fect upon the next device reset. c.23.1 syntax at+ab remotecommand [enable/disable] where [enable/disable] is an e or e character to enable this parameter and a d or d character to disable it. c.23.2 responses if the feature is successfully applied, the response is: at-ab remotecommand [enabled/disabled]
spbt2532c2.at commands doc id 16089 rev 1 37/51 c.24 remotecmddisconnect the remotecmddisconnect command is used to disconnect a remote command connection. this command only applies to the server side of the link; the remote device. the client or local device, if using the abserial interface, should use a sppdisconnect command since it is not in remote command mode. c.24.1 syntax at+ab remotecmddisconnect c.24.2 responses if the operation is successful, the response is: at-ab remotecmdmodeclosed c.25 reset the reset command is used to reset the abserial interface. this is provided in the event that a host application wants to perform a software reset for error recovery. there is a response prior to reset to verify the command was received by the abserial interface. c.25.1 syntax at+ab reset c.25.2 responses if the operation is successful, the response is: at-ab resetpending c.26 security the security command is used to set the security level of the device in use. by default, security level none is used. variable pin type (the pincode request event will always be received by the application from the stack), and 128-bit unit key. service level security, level 2, is not currently supported. the security setting is not preserved in non-volatile memory. c.26.1 syntax at+ab security [level] where [level] is the type of security to use: none link (default)
commands spbt2532c2.at 38/51 doc id 16089 rev 1 c.26.2 responses if the operation is successful, the response is: at-ab securityok c.27 smartcablesetup the smartcablesetup command is used enable and configure a smart cable device. a device?s bd address is specified with whic h to automatically establish a connection; replacing the need for at connection comma nds. this command will override the dynamic configuration of a smart cable device until the deletesmartcable command is issued; it is saved in non-volatile memory. c.27.1 syntax at+ab smartcablesetup [bd address] [attempts] [interval] where [bd address] is the bd address of the remote device to page and attempt to connect. [attempts] 0 ? 999 is the number of pages the will be atte mpted to the specified device until a connection is successful. a valu e of 0 will not automatically page the remote device, however, gpio 7 may be asserted to manually send a page. a value of 1000 will perform unlimited pages until connected. be switched to active mode. [sniff interval] is given in slots from 66-10,000. [interval] 1-1000 is the number of 100ms intervals (0.1sec to 100 sec) between page attempts. this interval is in addition to the amount of time required by the page attempt itself. c.27.2 responses if the operation is successful, the response is: at-ab smartcableconfigdone c.28 sniff the sniff command is used to switch a device from active mode to sniff mode. c.28.1 syntax at+ab sniff [bd address] [sniff interval] where [bd address] is the bd address of the device to be switched to active mode. [sniff interval] is given in slots from 66-10,000. c.28.2 responses if the operation is successful, the response is: at-ab sniffmode
spbt2532c2.at commands doc id 16089 rev 1 39/51 c.29 sppconnect the sppconnect command is used to initiate a connection with the specified device. the remote bd address must be specified. the remo te service is optional. if not specified, the first registered spp service will be used by default. c.29.1 syntax at+ab sppconnect [bd addr] [service] where [bd addr] is the remote devices bd address to page . [service] is the specific service on the remote device; optional. c.29.2 responses if the connection is successful, the response is: at-ab connectionup at-ab -bypassmode- if the connection cannot be completed, the response is: at-ab sppconnectionclosed c.30 sppdisconnect the sppdisconnect command is used to termin ate a connection with the remote device. c.30.1 syntax at+ab sppdisconnect c.30.2 responses if the connection is successful, the response is at-ab sppconnectionclosed
commands spbt2532c2.at 40/51 doc id 16089 rev 1 c.31 streamingserial c.31.1 syntax at+ab streamingserial [enable/disable] where [enable/disable] is an e or e character to enable this parameter and a d or d character to disable it. c.31.2 query an alternative syntax may be used to query the current streamingserial feature status. this syntax is not supporte d by other commands. at+ab streamingserial c.31.3 responses if the feature is successfully applied or queried, the response is: at-ab streamingserial [enabled/disabled] c.32 updateinquiryscan the updateinquiryscan command is used to modify the inquiry scan parameters: mode, duration, and interval. c.32.1 syntax at+ab updateinquiryscan [mode] [duration] [interval] where [mode] is the discoverable mode: 0: non-discoverable 1: limited discoverability ? not supported 2: discoverable [duration] is the scan length in slots; 18 to 4096. the default duration is 18 slots. [interval] is the period between scans in slots; 18 to 4096. the default interval is 2048 slots c.32.2 responses if the command is successf ul, the response is: at-ab inquiryscanupdatedone
spbt2532c2.at commands doc id 16089 rev 1 41/51 c.33 updatepagescan the updateinquiryscan command is used to modify the page scan parameters: mode, duration, and interval. c.33.1 syntax at+ab updatepagescan [mode] [duration] [interval] where [mode] is the connectable mode: 0: non-connectable 1: connectable [duration] is the scan length in slots; 18 to 4096. the default duration is 18 slots. [interval] is the period between scans in slots; 18 to 4096. the default interval is 2048 slots c.33.2 responses if the command is successf ul, the response is: at-ab pagescanupdatedone c.34 version the version command is used to return the current version of the abserial interface. c.34.1 syntax at+ab version c.34.2 responses if the operation is successful, the response is: at-ab abserialver [x.y] where [x.y] is the current version of the abserial interface.
error responses spbt2532c2.at 42/51 doc id 16089 rev 1 appendix d error responses this chapter details the error responses th at occur under specif ic circumstances. there are seven error responses that can occur beyond error responses specific to a particular command (e.g., discovery). they are: errconnect errexecution errformat errinprogress errinvalidparam errnumparam errunknowncmd the following subsections detail the different error responses. these error responses replace the original error response at-ab errorcommand d.1 errconnect the errconnect error response will be sent if abserial has a valid connection established and the command cannot be executed while connected (even in the command mode). examples of commands that produce this error response are given in the following table. table 10. example commands that generate example reason at+ab security none changing security level while a connection is up. at+ab discovery performing a device discovery while a connection is up. at+ab sppconnect 00043e000000 establishing a connection to a device while a connection is exists with another.
spbt2532c2.at error responses doc id 16089 rev 1 43/51 d.2 errexecution the errexecution error response will be sent if the command cannot complete for any reason. examples of commands that produce this error response are given in the following table. d.3 errformat the errformat error response will be sent if abserial receiv es a command (t ext terminated by a carriage return or line feed) that does not match the expected format of starting with at+ab . examples of commands that produce this error response are given in the following table. table 11. example commands that generate example reason at+ab security none execution of command with correct syntax failed at+ab discovery execution of command with correct syntax failed table 12. example commands that generate example reason at-ab discovery a valid command name that d oes not start with the right prefix. sppconnect 00043e000000 a command does not start with at+ab abcdef a command does not start with at+ab
error responses spbt2532c2.at 44/51 doc id 16089 rev 1 d.4 errinvalidparam the errinvalidparam error resp onse will be sent if the pa rameters for the requested command are not correct. the parameter(s) will be echoed back to the user starting from the parameter that was rejected. examples of commands that produce this error response are given in the following table. d.5 errnumparam the errnumparam error response will be sent if there are too few parameters for the requested command. a command sent with too many parameters does not generate an error; instead, the extra parameters are ignored. warning: some commands will accept a variable number of parameters. examples of commands that produce this error response are given in the following table. table 13. example commands that generate example response reason at+ab sppconnect 8136 at-ab errinvalidparam 8136 numeric parameter not specified with required number of digits (bd address must always be 12 hex characters). at+ab sppconnect 00043e008136 goep at-ab errinvalidparam goep unrecognized (or unsupported) symbolic parameter used. at+ab changebaud 1600 at-ab errinvalidparam 1600 numeric parameter is out of range (specified baud rate is not supported by command). at+ab enablebond 00043e000000 12345678901234567 at-ab errinvalidparam 12345678901234567 string parameter (pin)has too many characters. table 14. example commands that generate example reason at+ab security no parameters were specified. at+ab sniff the minimum number of parameters was not specified.
spbt2532c2.at error responses doc id 16089 rev 1 45/51 d.6 errunknowncmd the errunknowncmd error response will be sent if the reques ted command is not recognized. the unrecognized command will be echoed back to the host. any parameters given will be ignored. at-ab errunknowncmd [unrecognized command] an accepted command always starts with the command identifier: at+ab d.7 errinprogress errinprogress is sent in response to discovery command being issued when the previous one is still in progress. at+ab discovery [unrecognized command] examples of commands that produce this error response are given in the following table: table 15. example commands that generate example reason at+ab discovery trying to do discovery when the previous one has not completed .
error responses spbt2532c2.at 46/51 doc id 16089 rev 1 d.8 commands and associated errors the table below summarizes which of the commands produce specific error responses. if a command can produce an error response, the column will be marked with an x. table 16. possible errconnect error responses example errinvalidparam errnumparam er rexecute errconnect errinprogress bond x x x build bypass changebaud x x changedefaultbaud x x defaultlocalname x x deletesmartcable disablebond discovery x x x x dunconnect x x x dundisconnect enablebond x x x erasebondtable exitpark x x exitsniff x x gpioconfig x x gpioread x gpiowrite x x hold x x x localname x x park x x x remotecmddisconnect reset security x x x smartcablesetup x x sniff x x x sppconnect x x x sppdisconnect updateinquiryscan x x x updatepagescan x x x version
spbt2532c2.at other responses doc id 16089 rev 1 47/51 appendix e other responses the following subsections describe the 4 types of responses that occur under specific circumstances, not necessarily as a result of a specific command. they are: reset escape sequence controlled disconnect unexpected disconnect e.1 reset upon either hardware reset or software re set (such as the reset command), abserial will respond as follows after the reset is complete: at-ab -commandmode- at-ab bdaddress [bd addr] because the bd address of the local device is reported during this response, the response is different than a response to the escape sequence. e.2 escape sequence if the escape sequence, ^#^$^% , is received and no connection is active, abserial will immediately respond with: at-ab -commandmode- when the escape sequence is re ceived while a connection is still active and there is no data for 2 seconds, abserial will respond (after thos e 2 seconds of no data) with the same string. abserial will now be in command mode. e.3 controlled disconnect if the local host initiates a disconnect, it must first put the abserial interface into command mode (see the section on escape sequence directly above). after a successful disconnect command, the following response is made: at-ab connectiondown
other responses spbt2532c2.at 48/51 doc id 16089 rev 1 e.4 unexpected disconnect bluetooth connections may be unexpectedly dropped (e.g., in changing rf conditions). although it is generally a ssumed that a disconnect will be negotiated on th e application level, the remote device may initiate a disconnect. when that happens, the disconnect may be unexpected. this section applies to both the general case and the unexpected disconnect. it is useful for the local host to be notified that a connection has been terminated when it isn?t controlling the terminatio n. an unexpected disconnect is e ssentially defined as a disconnect that occurs while in bypa ss mode. if this happens, abserial will respond with: ###no carrier at-ab -commandmode- it is the responsibility of the ho st to prevent this string from appearing in the data stream during normal operation. if a remote disconnect occurs during command mode, this notification string is also sent. it will not be sent, however, if an initial setup cannot be establis hed or if the disconnect is requested by the local device. hardware handshaking is not used to indicate a disconnection in this implementation. modems can use dcd (data carrier detect) to notify the dte (data terminal entity, e.g., computer) that a connection is either available or unavailable.
spbt2532c2.at ordering information scheme doc id 16089 rev 1 49/51 ordering information scheme note: no antenna on board table 17. ordering information scheme spbt 2532 c2 .at bluetooth ? modules v2.1 compliant class 2 at command set
revision history spbt2532c2.at 50/51 doc id 16089 rev 1 revision history table 18. document revision history date revision changes 07-aug-2009 1 first release
spbt2532c2.at doc id 16089 rev 1 51/51 please read carefully: information in this document is provided solely in connection with st products. stmicroelectronics nv and its subsidiaries (?st ?) reserve the right to make changes, corrections, modifications or improvements, to this document, and the products and services described he rein at any time, without notice. all st products are sold pursuant to st?s terms and conditions of sale. purchasers are solely responsible for the choice, selection and use of the st products and services described herein, and st as sumes no liability whatsoever relating to the choice, selection or use of the st products and services described herein. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted under this document. i f any part of this document refers to any third party products or services it shall not be deemed a license grant by st for the use of such third party products or services, or any intellectual property contained therein or considered as a warranty covering the use in any manner whatsoev er of such third party products or services or any intellectual property contained therein. unless otherwise set forth in st?s terms and conditions of sale st disclaims any express or implied warranty with respect to the use and/or sale of st products including without limitation implied warranties of merchantability, fitness for a parti cular purpose (and their equivalents under the laws of any jurisdiction), or infringement of any patent, copyright or other intellectual property right. unless expressly approved in writing by an authorized st representative, st products are not recommended, authorized or warranted for use in milita ry, air craft, space, life saving, or life sustaining applications, nor in products or systems where failure or malfunction may result in personal injury, death, or severe property or environmental damage. st products which are not specified as "automotive grade" may only be used in automotive applications at user?s own risk. resale of st products with provisions different from the statements and/or technical features set forth in this document shall immediately void any warranty granted by st for the st product or service described herein and shall not create or extend in any manner whatsoev er, any liability of st. st and the st logo are trademarks or registered trademarks of st in various countries. information in this document supersedes and replaces all information previously supplied. the st logo is a registered trademark of stmicroelectronics. all other names are the property of their respective owners. ? 2009 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - belgium - brazil - canada - china - czech republic - finland - france - germany - hong kong - india - israel - ital y - japan - malaysia - malta - morocco - philippines - singapore - spain - sweden - switzerland - united kingdom - united states of america www.st.com

▲Up To Search▲

Price & Availability of SPBT2532C2AT

	To Download SPBT2532C2AT Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .